Repository navigation
release: 0.124.0 - #202
Open
kernel-internal[bot] wants to merge 2 commits into
Open
release: 0.124.0#202kernel-internal[bot] wants to merge 2 commits into
kernel-internal[bot] wants to merge 2 commits into
Conversation
Stainless-Generated-From: ddefaef675badfba8cf9582b6c68d9a94df54d22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.124.0 (2026-10-10)
Features
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
High Risk
Adds payment transaction reporting and merchant metadata on vault card flows, which affects financial reconciliation and must be called with correct observed outcomes.
Overview
Release 0.124.0 bumps package version and changelog; the functional change is in vault item APIs for Kernel Visa cards.
Clients can invoke a new
confirm_transactionvault item operation viaVaultItemPerformOperationParams.OfConfirmTransaction, usingConfirmTransactionVaultItemOperationRequestParamto report observed merchant outcomes (status, transaction type, amount, currency, timestamp)—explicitly not inferred from checkout fill alone. Available-operation metadata on credential, card, and wallet vault items now includesconfirm_transaction.Kernel card specs and related union types gain optional
merchant_categoryandmerchant_category_codefields (plus union getters), for supplying real MCC/category data when known.Reviewed by Cursor Bugbot for commit 041e2a1. Bugbot is set up for automated code reviews on this repo. Configure here.